Methods and Systems for Providing a Vehicle Repair Tip

ABSTRACT

A method performed by a first computing system includes receiving, from a second computing system, a message identifying a symptom of a first vehicle; and sending a repair tip to the second computing system. The repair tip includes a first phrase describing a first procedure performed on a second vehicle that exhibited the symptom, wherein the first procedure performed on the second vehicle yielded a result insufficient to determine that a component of the second vehicle associated with the symptom is defective. The repair tip also includes a second phrase describing a second procedure performed on a given vehicle, wherein the given vehicle is either (i) the second vehicle or (ii) a third vehicle that also exhibited the symptom, wherein the second procedure performed on the given vehicle yielded a result sufficient to determine that a component of the given vehicle associated with the symptom is defective.

REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 16/003,150, filed on Jun. 8, 2018. U.S. patentapplication Ser. No. 16/003,150 is a continuation application of U.S.patent application Ser. No. 15/499,399, filed on Apr. 27, 2017. U.S.patent application Ser. No. 15/499,399 is a continuation application ofU.S. patent application Ser. No. 14/938,662, filed on Nov. 11, 2015.U.S. patent application Ser. No. 14/938,662 issued on May 30, 2017 asU.S. Pat. No. 9,665,994. U.S. patent application Ser. No. 15/499,399issued on Jun. 26, 2018 as U.S. Pat. No. 10,008,050. U.S. patentapplication Ser. No. 14/938,662, U.S. patent application Ser. No.15/499,399, and U.S. patent application Ser. No. 16/003,150 areincorporated herein by reference.

BACKGROUND

Many products produced by manufacturers occasionally have to berepaired. Many owners are unequipped or otherwise unable to repaircertain products. Such owners may depend on professional repairtechnicians to service or repair the owner's product.

Product manufacturers use a significant amount of resources (e.g., humanand financial) to generate repair information, such as repair manualsand technical service bulletins, that repair technicians can referencewhile diagnosing and repairing a product.

OVERVIEW

Example embodiments are described herein. In a first aspect of thisdescription, one or more example embodiments can be arranged as acomputer-readable medium storing instructions that, when executed by afirst computing system, cause the first computing system to performfunctions. The functions include receiving, from a second computingsystem, a message identifying a symptom of a first vehicle and sending arepair tip to the second computing system.

The repair tip includes a first phrase describing a first procedureperformed on a second vehicle that exhibited the symptom. The firstprocedure performed on the second vehicle yielded a result insufficientto determine that a component of the second vehicle associated with thesymptom is defective. The repair tip also includes a second phrasedescribing a second procedure performed on a given vehicle. The givenvehicle is either (i) the second vehicle or (ii) a third vehicle thatalso exhibited the symptom. The second procedure performed on the givenvehicle yielded a result sufficient to determine that a component of thegiven vehicle associated with the symptom is defective. The component ofthe given vehicle is equivalent to the component of the second vehicle.

In a second aspect of this description, one or more example embodimentscan be arranged as a method performed by a first computing system. Themethod includes receiving, from a second computing system, a messageidentifying a symptom of a first vehicle and sending a repair tip to thesecond computing system. The repair tip includes a first phrasedescribing a first procedure performed on a second vehicle thatexhibited the symptom. The first procedure performed on the secondvehicle yielded a result insufficient to determine that a component ofthe second vehicle associated with the symptom is defective. The repairtip also includes a second phrase describing a second procedureperformed on a given vehicle. The given vehicle is either (i) the secondvehicle or (ii) a third vehicle that also exhibited the symptom. Thesecond procedure performed on the given vehicle yielded a resultsufficient to determine that a component of the given vehicle associatedwith the symptom is defective. The component of the given vehicle isequivalent to the component of the second vehicle.

In a third aspect of this description, one or more example embodimentscan be arranged as a first computing system. The first computing systemincludes one or more processors and a non-transitory computer-readablemedium storing instructions, that when executed by the one or moreprocessors, cause the first computing system to perform functions. Thefunctions include receiving, from a second computing system, a messageidentifying a symptom of a first vehicle and sending a repair tip to thesecond computing system. The repair tip includes a first phrasedescribing a first procedure performed on a second vehicle thatexhibited the symptom. The first procedure performed on the secondvehicle yielded a result insufficient to determine that a component ofthe second vehicle associated with the symptom is defective. The repairtip also includes a second phrase describing a second procedureperformed on a given vehicle. The given vehicle is either (i) the secondvehicle or (ii) a third vehicle that also exhibited the symptom. Thesecond procedure performed on the given vehicle yielded a resultsufficient to determine that a component of the given vehicle associatedwith the symptom is defective. The component of the given vehicle isequivalent to the component of the second vehicle.

These as well as other aspects and advantages will become apparent tothose of ordinary skill in the art by reading the following detaileddescription, with reference where appropriate to the accompanyingdrawings. Further, it should be understood that the embodimentsdescribed in this overview and elsewhere are intended to be examplesonly and do not necessarily limit the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments are described herein with reference to the followingdrawings.

FIG. 1 is a block diagram of networked computing systems.

FIG. 2 is a block diagram of a computing system.

FIG. 3 is a block diagram of a computing system.

FIG. 4 is a flowchart depicting an example method.

FIG. 5 shows an example repair tip.

FIG. 6 shows an example data table stored by a computing system.

FIG. 7 shows example phrase templates.

FIG. 8 shows example phrases.

FIG. 9 shows additional example phrases.

DETAILED DESCRIPTION I. Introduction

Traditionally, when diagnosing a symptom of a vehicle and repairing thevehicle to address the symptom, a repair technician might consult arepair manual that is in paper form or in an electronic format stored ona computing device. In either case, the paper or electronic repairmanual may become dated as time passes and the repair technician may beunaware of new techniques for repairing the vehicle that other repairtechnicians have discovered. Therefore, it may be useful for up-to-daterepair data submitted by many such repair technicians to be available ona database that is shared among repair technicians. The database may beaccessible via electronic vehicle repair tools and/or other computingdevices. It may also be useful to provide repair tips in the form ofrandomly varying phrase formats to better catch the attention of arepair technician that is viewing the repair tip.

For purposes of this description, a vehicle is a mobile machine that maybe used to transport a person, people, or cargo. As an example, anyvehicle described herein may be driven or otherwise guided along a path(e.g., a paved road or otherwise) on land, in water, or in the air orouter space. As another example, any vehicle described herein may bewheeled, tracked, railed or skied. As yet another example, any vehicledescribed herein may include an automobile, a motorcycle, an all-terrainvehicle (ATV) defined by ANSI/SVIA-1-2007, a snowmobile, a personalwatercraft (e.g., a JET SKI® personal watercraft), a light-duty truck, amedium-duty truck, a heavy-duty truck, a semi-tractor, or a farmmachine. As still yet another example, any vehicle described herein mayinclude or use any appropriate voltage or current source, such as abattery, an alternator, a fuel cell, and the like, providing anyappropriate current or voltage, such as about 12 volts, about 42 volts,and the like. As still yet another example, any of the vehiclesdescribed herein may include or use any desired system or engine. Thosesystems or engines may include items that use fossil fuels, such asgasoline, natural gas, propane, and the like, electricity, such as thatgenerated by a battery, magneto, fuel cell, solar cell and the like,wind and hybrids or combinations thereof. As still yet another example,any vehicle described herein may include an electronic control unit(ECU), a data link connector (DLC), and a vehicle communication linkthat connects the DLC to the ECU.

Although many of the example embodiments are described with respect to avehicle, the example embodiments can be applicable to products orrepairable items other than a vehicle. As an example, the other productsor repairable items can include home appliances, such as a generator, arefrigerator, a dishwasher, or a washing machine, or a consumerelectronic device, such as a television, a cellular phone, or a tabletdevice. Other examples of the other products or repairable items arealso possible. Accordingly, for embodiments based on these otherproducts or repairable items, the term vehicle in the describedembodiments can be replaced with a name of the other product orrepairable item.

In this description, the articles “a” or “an” are used to introduceelements of the example embodiments. Any reference to “a” or “an” refersto “at least one,” and any reference to “the” refers to “the at leastone,” unless otherwise specified, or unless the context clearly dictatesotherwise. The intent of using those articles is that there is one ormore of the elements.

The intent of using the conjunction “or” within a described list of atleast two terms is to indicate any of the listed terms or anycombination of the listed terms. The use of ordinal numbers such as“first,” “second,” “third” and so on is to distinguish respectiveelements rather than to denote a particular order of those elements. Forpurpose of this description, the terms “multiple” and “a plurality of”refer to “two or more” or “more than one.”

The block diagram(s) and flow chart(s) shown in the figures are providedmerely as examples and are not intended to be limiting. Many of theelements illustrated in the figures or described herein are functionalelements that can be implemented as discrete or distributed elements orin conjunction with other elements, and in any suitable combination andlocation. Those skilled in the art will appreciate that otherarrangements and elements (e.g., machines, interfaces, functions,orders, or groupings of functions) can be used instead. Furthermore,various functions described as being performed by one or more elementsof a machine described herein can be carried out by a processorexecuting computer-readable program instructions or by any combinationof hardware, firmware, or software.

II. Example Architecture

FIG. 1 is a block diagram of a system 100 in accordance with one or moreexample embodiments. Various combinations of the elements shown in FIG.1 can be arranged as other systems or as a sub-system to carry outexample embodiments described herein. System 100 includes a computingsystem 102 (e.g., a vehicle repair data (VRD) system) and a network 104.Network 104 can include a wide area network (WAN), such as the Internetor a portion thereof. Additionally or alternatively, network 104 caninclude a wireless network, a wired network, a local area network (LAN),or some other type of network. Network 104 can include two or more ofthe aforementioned example networks.

System 100 includes computing systems 108, 110, 112, 116, 118, and 120.The computing systems 108-120 may take the form of a vehicle repair tool(VRT). Any of the computing systems 108-120 described herein can be, butis not required to be, configured to generate or transmit an originalrepair order (RO) to computing system 102. The operator of computingsystem 102 can enter an original RO into computing system 102 using anRO manual entry device, such as an RO manual entry device 202 shown inFIG. 2. The manually-entered RO can be stored in a data storage device,such as a data storage device 210 shown in FIG. 2.

Computing systems 108-120 may represent vehicle repair tools that areconfigured to perform various functions. For example, any of thecomputing systems 108-120 may send a request, to computing system 102,for a repair tip that is stored at and/or generated by computing system102. The request may be sent using network 104. Any of the computingsystems 108-120 may also receive a repair tip transmitted from computingsystem 102 using network 104 or otherwise provided or generated bycomputing system 102. Any of the computing systems 108-120 may alsopresent a received repair tip via a user interface.

Next, FIG. 2 is a block diagram showing details of a computing system102 (e.g., a vehicle repair data (VRD) system). Computing system 102 cancomprise, be configured as, or be referred to as a server system, aserver device, or more simply, a server. In accordance with embodimentsin which computing system 102 operates as a server, computing system 102can serve one or more computing systems 108-120 (e.g., vehicle repairtools (VRT)) operating as a client device to the server.

Computing system 102 includes the RO manual entry device 202, aprocessor 204, a user interface 206, a network interface 208, and a datastorage device 210, all of which can be linked together via a systembus, network, or other connection mechanism 212.

RO manual entry device 202 can include one or more devices for inputtingdata shown on a printed RO into computing system 102 for storage as anoriginal RO within repair orders (RO) 214. As an example, RO manualentry device 202 can include a scanner device with or without an opticalcharacter recognition software application. As another example, ROmanual entry device 202 can include a keyboard for keying in (e.g.,typing) the data shown on the printed RO and sending the keyed in (e.g.,typed or otherwise entered) data to processor 204 for storage as anoriginal RO within RO 214. As yet another example, RO manual entrydevice 202 can include a device that accepts data storage devices, suchas a CD-ROM including data representing an original RO generated by aVRT. As yet another example, RO manual entry device 202 can include alaptop or desktop computing device with or connected to a display.

An original RO can be displayed by RO manual entry device 202 or userinterface 206. For any of a variety of reasons, such as security ofinformation located on an original RO, Computing system 102 can beconfigured such that an original RO generated by a first computingsystem, such as computing system 108, is not provided to a secondcomputing system, such as computing system 116. In other examples,computing system 102 can generate a presentable RO based, at least inpart, on information on the original RO generated by the computingsystem 108, and provide the presentable RO to computing system 116.

A processor, such as processor 204, can include one or more generalpurpose processors (e.g., INTEL single core microprocessors or INTELmulticore microprocessors) or one or more special purpose processors(e.g., digital signal processors). A processor, such as processor 204,can be configured to execute computer-readable program instructions,such as computer-readable program instructions (CRPI) 218. For purposesof this description, processor 204 executing CRPI 218 to perform somefunction described herein can include executing a portion of CRPI 218 orthe entirety of CRPI 218. Executing a portion or the entirety of CRPI218 can include executing some of the computer-readable programinstructions multiple times.

User interface 206 can include an interface to components operable toreceive input, data, or information into computing system 102 or tocomponents that can present data or information output for computingsystem 102. Those components can be referred to as user interfacecomponents. User interface 206 can include one or more audio/visualports or communication ports that connect to a user interface componentby a wired or wireless user interface communication link.

User interface 206 can include one or more of the user interfacecomponents. As an example, the user interface components can include aninfrared remote control device, a display device, a loud speakerconfigured to convert electrical signals to audible sounds, a keyboard,a touch screen, a pointing device, such as a computer mouse, or someother component for generating signals to enter data or information intocomputing system 102 or to present data or information output by userinterface 206.

User interface 206 can include a transmitter or transceiver to providethe data or information to another user interface component or toanother element of computing system 102. The data or informationprovided by user interface 206 can include, but is not limited toinclude, a repair tip of repair tips 220.

Network interface 208 can include an interface to one or morecommunication networks, such as network 104. For use with wirelesscommunication networks, network interface 208 can include one or moreantennas for transmitting or receiving wireless communications. Networkinterface 208 can include one or more communication ports configured toconnect to a wired communication link of a network, such as a coaxialcable, an Ethernet cable, a fiber optic cable, a digital subscriber line(DSL), a telephone line of a public switched telephone network (PSTN) orsome other wired connector. Network interface 208 can include a networkcontroller including a transmitter, a receiver, or a transceiver. Thetransmitter or transceiver can provide data or information to acommunication port for transmission as network communications over theconnected network. The receiver or transceiver can receive data orinformation received at a communication port from the connected network.

A data storage device, such as data storage device 210, can include anon-transitory computer-readable storage medium readable by processor204. In an alternative arrangement, data storage device 210 can includetwo or more non-transitory computer-readable storage mediums. Eachnon-transitory computer-readable storage medium can include volatile ornon-volatile storage components, such as optical, magnetic, organic orother memory or disc storage, which can be integrated in whole or inpart with a processor, such as processor 204.

Data storage device 210 can store a variety of data. The data stored bydata storage device 210 can be data that was provided to data storagedevice 210 for storage from RO manual entry device 202, processor 204,user interface 206 or network interface 208. As shown in FIG. 2, datastorage device 210 can store repair orders (RO) 214, a taxonomy termdatabase 216, computer-readable program instructions (CRPI) 218, repairtips 220, meta-data 222, vehicle leverage data 224, parts leverage data226, text strings 228, and search terms 230. Search terms 230 caninclude, but is not limited to, vehicle-identification (i.e.,vehicle-ID) search terms 232, such as year/make/model/engine (Y/M/M/E)attributes, and symptom criterion 234.

RO 214 can include computer-readable RO. The computer-readable RO can bearranged as a structured query language (SQL) file, an extensible markuplanguage (XML) file, or some other type of computer-readable file ordata structure. The RO within RO 214 can be received from RO manualentry device 202, from network interface 208 by way of network 104, orfrom another device. The RO within RO 214 can be an original RO, such asRO generated by a computing system 108-120 shown in FIG. 1 or enteredusing RO manual entry device 202, or a presentable RO generated bycomputing system 102.

Mapping, standard, context terms, or labor operation codes can be storedas part of taxonomy term database 216. Taxonomy term database 216 caninclude data that identifies words or phrases that are associated withone another. The association can be based on the words or phrases havinga common meaning. The words or phrases identified as being associatedwith one another can be referred to a “taxonomy database group” or, moresimply, a “taxonomy group.”

Taxonomy term database 216 can include one or more taxonomy groups, andeach taxonomy group can include one or more taxonomy terms (e.g., wordsor phrases). As an example, taxonomy term database 216 can include datathat identifies the following phrases as a taxonomy group: (i) stallswhen cold, (i) engine quits when temperature is low, (iii) engine diesin the morning, (iv) dies in the morning, (v) dies in the AM, and (vi)engine stalls on cold mornings.

Each taxonomy group can be associated with a standard term, which couldbe a first word or first phrase added to the taxonomy group.Alternatively, a word or phrase subsequently added to the taxonomy groupcan be the standard term for the taxonomy group. The words or phrasesother than the standard term within a taxonomy group can be mappingterms. The words or phrases within each taxonomy group can be obtainedfrom an RO. An administrator can approve adding or modifying anytaxonomy group by, for example, processor 204 executing CRPI 218. Termswithin taxonomy term database 216 can be compared to terms on acomputer-readable RO. A mapping term on an original RO and found withina given taxonomy group can be represented on a presentable RO by astandard term for the given taxonomy group.

Processor 204 can search the text, symbols or other content on an RO ofRO 214 or the meta-data associated with an RO to associate an RO withina cluster of RO (or more simply, an RO cluster). Each cluster of RO canbe associated with defined RO attributes, such as a diagnostic troublecode (DTC), action, or component listed on the RO. Other attributes ofthe information recorded on an RO can be associated with an RO cluster.Table 1 shows data identifying twenty-five clusters identified with ID 1through 25, inclusive. The cluster size indicates how many RO have beenassociated with the respective cluster. The cluster size can be modifiedas or after additional RO are added to RO 214. Table 1 shows examples ofDTC, Action, and component attributes associated with each respective ROcluster.

TABLE 1 Cluster Cluster ID Size DTC Action Component(s) 1 3,101 P0303Replaced Ignition Coil 2 3,086 P0303 Replaced Spark Plug 3 2,982 P0302Replaced Ignition Coil 4 2,957 P0304 Replaced Spark Plug 5 2,831 P0171Replaced Oxygen Sensor 6 2,813 P0325 Replaced Knock Sensor 7 2,762 P0301Replaced Spark Plug 8 2,713 P0320 Replaced Crankshaft Position Sensor 92,624 P0404 Replaced Exhaust Gas Recirculation Valve 10 2,609 P0302Replaced Spark Plug 11 2,603 P0303 Replaced Spark Plug Wire, Spark Plug12 2,328 P0161 Replaced Oxygen Sensor 13 2,324 C1500 Replaced FuelFilter, Fuel Tank Module 14 2,232 P0301 Replaced Spark Plug Wire, SparkPlug 15 2,225 P0302 Replaced Spark Plug Wire, Spark Plug 16 2,107 P0300Replaced Ignition Coil 17 2,104 P0305 Replaced Ignition Coil 18 2,088P0171, Replaced Mass Airflow Sensor P0174 19 2,007 P0134 Replaced OxygenSensor 20 1,991 P0304 Replaced Spark Plug Wire, Spark Plug 21 1,963P0171, Replaced Fuel Filter P0174 22 1,952 P0306 Replaced Ignition Coil23 1,899 P0128 Replaced Thermostat Housing, Engine Coolant Thermostat 241,824 P0125 Replaced Engine Coolant Thermostat 25 1,783 P0031 ReplacedOxygen Sensor

Table 1 can be modified to include a separate column for otherattributes as well. The other attributes can identify RO attributes suchas, but not limited to, a customer complaint, a date, or a laboroperation code (LOC). As an example, the customer complaint can include,but is not limited to, terms such as rattles, won't start, and vibrates.Repair tips for those example customer complaint terms can includerepair tips identifying a way to stop a vehicle from rattling, a way tofix a vehicle that does not start, and a way to stop a vehicle fromvibrating, respectively.

Table 2 below shows an example of data included on 25 of the 2,088 ROassociated with the RO cluster ID 18 shown in Table 1. The RO data inTable 2 includes an RO identifier that can, for example, be assigned bya VRT or computing system 102. The RO data in Table 2 also includesyear/make/model/engine attributes associated with each RO.

TABLE 2 RO ID Year Make Model Engine 2197 1999 Cadillac Catera 3.0 L V6,VIN (R) 9277 1998 Mercury Grand Marquis 4.6 L V8, VIN (W) GS 1156 2002Ford Pickup F150 4.2 L, V6 VIN (2) 6978 2003 Ford Taurus SE 3.0 L V6,VIN (U) 7923 1999 Ford Pickup F150 4.6 L V8, VIN (W) 5074 2000 InfinitiI30 3.0 L V6, VIN (C) 5640 1997 Ford Cutaway E350 6.8 L, V10, VIN (S)1037 2002 Land Range Rover 4.6 L, V8, VIN (4) Rover HSE 1509 2002 FordExplorer 4.0 L, V6-245, SOHC 1673 2006 Ford Explorer 4.0 L, V6-245, SOHC2088 1998 Ford Cutaway E350 6.8 L, V10, VIN (S) 4692 2006 Ford PickupF250 5.4 L, V8 VIN (5) Super Duty 5183 1996 Mercury Grand Marquis 4.6 L,V8, VIN (W) GS MFI 6825 2000 Saturn LS2 3.0 L, V6, VIN (R) 8203 2001Hyundai XG300 3.0 L V6, VIN (D) 3915 1997 Ford Crown Victoria 4.6 L, V8,VIN (W) LX 7481 2001 Nissan Pathfinder SE 3.5 L, V6-3498, DOHC 7833 2007Chevrolet Silverado 6.0 L, V8, VIN (U) Classic 7976 1997 FordThunderbird LX 4.6 L, V8, VIN (W) 9892 2000 Nissan Maxima GLE 3.0 L V6,VIN (C) 0156 1999 Ford Econoline E150 4.6 L, V8, VIN (6) 1194 2002 FordPickup F150 4.2 L V6, VIN (2) 8797 2006 Ford Crown Victoria 4.6 L V8,VIN (W) LX 6321 2000 Ford Explorer 4.0 L V6, VIN (X) 6924 1998 FordRanger 4.0 L V6, VIN (X)

Some vehicle models are associated with a sub-model attribute. Somevehicle models are not associated with a sub-model attribute. Table 2can be modified to include a separate column to include sub-modelattributes for vehicles that are associated with a sub-model attribute.As an example, RO ID 7923 pertains to a Ford Pickup F150 make and model.The term “F150” can be referred to as a sub-model attribute. Othersub-model attributes for Ford Pickup models can include the “F250” and“F350” sub-model attributes. A sub-model attribute can be included on anRO. Searching for RO or repair tips based on a sub-model in addition toY/M/M/E attributes can lead to search results having RO or repair tipsassociated with a particular sub-model, but not the other sub-model(s)of a particular vehicle having particular Y/M/M/E attributes. The “S”within Y/M/M/S/E can represent a sub-model attribute.

Table 2 can be modified to include a separate column for otherattributes as well. The other attributes can identify system (Sys)attributes such as, but not limited to, a transmission attribute, asuspension attribute, and an audio system attribute. A set of attributesincluding a system attribute can be referred to as Y/M/M/E/Sysattributes.

Vehicle leverage data 224 can include computer-readable data thatidentifies different vehicle models built on a common vehicle platform.Vehicles built on a common vehicle platform can have many similaritiesincluding the use of common parts or part numbers. Vehicles built on acommon platform can experience similar vehicle symptoms that arise forsimilar reasons, such as failure of a part common to vehicles built onthe common vehicle platform. Table 3 shows an example of data that canbe stored as vehicle leverage data 224.

Processor 204 can generate an RO cluster that covers multiple vehiclemodels, such as the three vehicle models of VLD-3 shown in Table 3. IfRO 214 includes 100 RO for the Chevrolet Lumina APV model between1990-1996 and a given repair condition, 150 RO for the Pontiac TranSport models between 1990-1996 and the given problem, and 40 RO for theOldsmobile Silhouette model between 1990-1196 and the given problem,processor 204 can generate three separate RO clusters for the 290 RO ora single RO cluster for the 290 RO. A greater quantity of RO canindicate a greater likelihood of a successful repair of the givenproblem.

TABLE 3 Vehicle Leverage Data Identifier Model (VLD ID) Vehicle ModelsYear(s) Exceptions VLD-1 Cadillac Escalade, 2011-2013 GMC Yukon usesChevrolet Tahoe, Chevrolet hi-capacity Suburban, GMC Yukon radiatorVLD-2 Chevrolet Lumina APV, 1990-1996 N.A. Pontiac Trans Sport,Oldsmobile Silhouette VLD-3 Buick Regal, Oldsmobile 1998-2002 N.A.Intrigue VLD-4 Ford Expedition, 2008-2014 Lincoln Navigator LincolnNavigator uses aluminum cylinder heads

Processor 204 can use the exception data within vehicle leverage data224 to exclude RO pertaining to certain vehicle models from an ROcluster associated with a group of vehicles built on a common platform.For the exception data in Table 3, since the GMC Yukon uses a differentradiator than the Cadillac Escalade, the Chevrolet Tahoe, and theChevrolet Suburban, an RO cluster pertaining to a radiator for a GMCYukon may not be grouped with an RO cluster pertaining to a radiator onCadillac Escalades, Chevrolet Tahoes, and Chevrolet Suburbans.

Parts leverage data 226 can include data that identifies differentvehicle models that use a common part produced by one or more part(s)manufacturer. For purposes of this description, a common part is a partthat can be used in either of two or more vehicle models withoutaltering the part or any of the two or more vehicles to use the commonpart. Various references to a common part, such as a part number or partname, used by any or all of the part(s) manufacturer and themanufacturer(s) of the different vehicle models can be used. Vehiclemodels using a common part can experience similar vehicle symptoms thatarise for similar reasons, such as failure of the common part. Table 4shows an example of data that can be stored as parts leverage data 226.

TABLE 4 Common Vehicle Part Common Vehicle Model Part(s) IdentifierVehicle Part Models Year(s) manufacturer PLD-1 Coolant Cadillac 2012Delco Parts, temperature Escalade Inc. sensor PLD-1 Coolant Chevrolet2012 Delco Parts, temperature Tahoe Inc. sensor PLD-1 Coolant Chevrolet2012 Delco Parts, temperature Suburban Inc. sensor PLD-2 Fuel Honda 2013ACME, Inc. injector(s) Accord PLD-2 Fuel Honda 2013 ACME, Inc.injector(s) Civic

Processor 204 can generate an RO cluster that covers a common vehiclepart and multiple vehicle models, such as the coolant temperature sensorand three vehicle models of PLD-1 shown in Table 4. If RO 214 includes30 RO for the 2012 Cadillac Escalade model and the coolant temperaturesensor, 40 RO for the 2012 Chevrolet Tahoe model and the coolanttemperature sensor, and 20 RO for the 2012 Chevrolet Suburban model andthe coolant temperature sensor, processor 204 can generate threeseparate RO clusters for the 90 RO or a single RO cluster for the 90 RO.A greater quantity of RO can indicate a greater likelihood of occurrenceof a successful repair of a given problem arising from the coolanttemperature sensor.

CRPI 218 can include program instructions executable by processor 204 tocarry out functions described herein or performable by computing system102. CRPI 218 can include program instructions that are executable toparse data from an original RO stored within RO 214 and to identify theservice procedure information, vehicle identification, and parts usageinformation from the original RO for use in generating a presentable ROor to increment a count of a cluster size if a presentable RO pertainingto the original RO has already been generated.

CRPI 218 can include program instructions executable by processor 204 togenerate, for each repair tip and based on the RO stored in RO 214,meta-data associated with at least one set of search terms. Meta-data222 can include meta-data generated by processor 204 based theinformation listed on original RO including, but not limited to the LOCand a definition of the LOC.

CRPI 218 can include program instructions executable by processor 204 todetermine that words or phrases within service procedure information,such as service procedure information are within one or more taxonomygroups of taxonomy term database 216, and to associate (e.g., relate)that service procedure information with the one or more taxonomy groups.The service procedure information associated with any given taxonomygroup can be part of a new RO cluster or additional service procedureinformation to be added to an RO cluster or to modify an RO cluster.

Text strings 228 (e.g., a phrase template or a phrase) can includestrings of text (e.g., two or more words, numbers or symbols). A textstring can include one or more gaps for inserting meta-data to completethe text string. A text string can include a complete text stringwithout any gaps. Processor 204 can select one or more text strings toassociate with a set of terms (e.g., search terms) that can be enteredor received to search for a repair tip of repair tips 220. Processor 204can select the meta-data to insert into the gap(s) of a text string.Text strings 228 can include text strings representing input received byuser interface 206. Text strings 228 can include text strings receivedby network interface 208.

Search terms 230 can include various sets of search terms. A set ofsearch terms can include vehicle-ID search terms 232 or a symptomcriterion 234. A first example set of search terms can include searchterms received by network interface 208 as part of a request for arepair tip. The first example set of search terms can include searchterms that are non-standard terms in taxonomy terms database 216 and canbe referred to as non-standard search terms (NSST). Processor 204 canidentify, within taxonomy term database 216, standard terms that matchthe search terms received by network interface 208 and then use anystandard terms included within the received search terms or identifiedfrom taxonomy term database 216 to search for a repair tip. Thenon-standard search terms stored as part of search terms 230 cansubsequently be reviewed by processor 204 or a human using RO manualentry device 202 or user interface 206 for inclusion as part of taxonomyterm database 216.

A second example set of search terms can include standard sets of searchterms and can be referred to as standard search terms (SST). A standardset of search terms can include standard vehicle-ID search terms, suchas Y/M/M/E attributes, defined in taxonomy term database 216 andstandard symptom criterion defined in taxonomy term database 216.Processor 204 can associate one or more standard sets of search termswith a repair tip or a repair order. A set of search terms associatedwith a repair tip or repair order can be stored as meta-data associatedwith that repair tip or repair order. Taxonomy term database 216 caninclude search terms 230. The second example set of search terms can beassociated with one more sets of search terms like the first example setof search terms.

Table 5 shows an example of search terms that can be stored in searchterms 230. NSST-227 is associated with SST-15. SST-15 is associated withRO ID 3915. A repair tip corresponding to RO ID 3915 can be identifiedin response to receiving NSST-227, determining that SST-15 is associatedwith NSST-227, and determining RO ID 3915 is associated with SST-15.SST-1456 is a set of standard search terms having symptom criterioncommon to SST-15 and SST-1456, and a Y/M/M/E attribute that differs fromthe Y/M/M/E for SST-15 only by the model years (i.e., 2000 instead of1999). SST-15 and SST-1456 are both associated with RO ID 3915. Thisassociation can be determined based on vehicle leverage data 224 orparts leverage data 226.

TABLE 5 Search Terms Y/M/M/E Symptom Criterion Associations NSST-227 97Ford Crown Emissions and MAF SST-15 Vic. 8 cyl. failed. DTC P171 P174.SST-15 1999/Ford/Crown Pcode: P0171, P0174 RO ID 3915 Victoria/4.6 LComponent: MAF sensor NSST-227 V8 (W) Work Requested: failed stateemissions certification SST-1456 2000/Ford/Crown Pcode: P0171, P0174 ROID 3915 Victoria/4.6 L Component: MAF sensor V8 (W) Work Requested:failed state emissions certification

The vehicle-ID search terms 232 is one example of search terms that canbe included within search terms 230. Vehicle-ID search terms 232 caninclude various selectable attributes. For example, the attributes ofvehicle-ID search terms 232 can include Y attributes. As anotherexample, the attributes of vehicle-ID search terms 232 can includeYear/Make/Model/Sub-model/Engine (Y/M/M/S/E) attributes as discussedwith respect to Table 2. As another example, the attributes ofvehicle-ID search terms 232 can include Year/Make/Model/Engine/System(Y/M/M/E/Sys) attributes. As another example, the attributes ofvehicle-ID search terms 232 can includeYear/Make/Model/Sub-model/Engine/System (Y/M/M/S/E/Sys) attributes.

The system (Sys) attribute vehicle-ID search terms 232 can indicate orrepresent a system (e.g., one or more systems) or a component (e.g., oneor more components) within a vehicle. As an example, the system orcomponent within the vehicle can identify (i) a powertrain transmissionwithin the vehicle (e.g., a 4-speed automatic transmission withover-drive), (ii) a rear differential within the vehicle (e.g., a reardifferential with a 4.11:1 gear ratio), (iii) an electric alternatorwithin the vehicle (e.g., a 100 ampere alternator), (iv) a heater,ventilation, and air-conditioning (HVAC) system installed within thevehicle (e.g., a dual-zone (e.g., a driver side and passenger side) HVACsystem), or some other system or component installed within, attachedto, or other otherwise operating on or in the vehicle.

The order of any of the vehicle-ID search terms 232 described herein canbe rearranged as desired. For example, the order of the Y/M/M/Eattributes could be rearranged as Make/Model/Engine/Year (M/M/E/Y)attributes or in another arrangement.

Next, FIG. 3 is a block diagram showing details of an example computingsystem 108 (e.g., a vehicle repair tool (VRT)). Computing system 108includes a user interface 302, a processor 304, a network interface 306,and a data storage device 308, all of which can be linked together via asystem bus, network, or other connection mechanism 310. One or more ofthe computing systems 108-120 shown in FIG. 1 can be arranged likecomputing system 108 and vice versa.

Processor 304 can be configured to execute computer-readable programinstructions, such as computer-readable program instructions (CRPI) 312stored within data storage device 308. For purposes of this description,processor 304 executing CRPI 312 to perform some function describedherein can include executing a portion of CRPI 312 or the entirety ofCRPI 312. Executing a portion or the entirety of CRPI 312 can includeexecuting some of the computer-readable program instructions multipletimes.

Data storage device 308 can include a non-transitory computer-readablestorage medium (i.e., two or more computer-readable storage mediums)readable by processor 304. The (or each) non-transitorycomputer-readable storage medium can include volatile or non-volatilestorage components, such as optical, magnetic, organic or other memoryor disc storage, which can be integrated in whole or in part with aprocessor 304.

User interface 302 can include an interface to components that areconfigured to receive input for the computing system 108 or tocomponents that are configured to present data or information output forcomputing system 108. Any of those components can be referred to as aVRT user interface component. User interface 302 can include one or moreaudio/visual ports or communication ports that connect to a VRT userinterface component by a wired or wireless user interface communicationlink. Data, input, or information received by computing system 108 viauser interface 302 can include data or information for preparing an RO.

User interface 302 can include one or more of the VRT user interfacecomponents. As an example, the VRT user interface components can includean infrared remote control device, a display device, a loud speakerconfigured to convert electrical signals to audible sounds, a keyboard,a touch screen, a pointing device, such as a computer mouse, or someother component for generating signals to enter data or information intocomputing system 108 or to present data or information output by userinterface 302. User interface 302 can include a transmitter ortransceiver to provide the data or information to another VRT userinterface component.

Network interface 306 can include an interface to one or morecommunication networks, such as network 104. For use with wirelesscommunication networks, network interface 306 can include one or moreantennas for transmitting or receiving wireless communications. Networkinterface 306 can include one or more communication ports configured toconnect to a wired communication link of a network. Examples of thewired communication link are listed elsewhere herein. Network interface306 can include a network controller including a transmitter, areceiver, or a transceiver. The transmitter or transceiver can providedata or information to a communication port for transmission as networkcommunications over the connected network. The receiver or transceivercan receive data or information received at a communication port fromthe connected network. The data or information provided by networkinterface 306 to the network can include an RO.

CRPI 312 can include program instructions for generating an RO, based oninput received by user interface 302 or a user interface componentthereof. CRPI 312 can include program instructions for performingdiagnostic functions for diagnosing a vehicle identified on an RO. As anexample, performing the diagnostic functions can include checking adiagnostic trouble code (DTC). CRPI 312 can include program instructionsfor (i) displaying, by user interface 302, vehicle-ID attributesselectable to form a set of search terms, symptom criterion selectableto form part of the set of search terms, and a field for entering ausage indicator (e.g., a vehicle mileage or hours of engine use), (ii)receiving a selection of the set of search terms, (iii) providing theselected set of search terms to network interface 306 for transmissionof the selected search terms to computing system 102, (iv) receiving, bynetwork interface 306, a repair tip from computing system 102, and (v)displaying the received repair tip using user interface 302.

III. Example Operation

FIG. 4 is a flowchart depicting a method 400 that can be carried out inaccordance with one or more example embodiments described herein. Themethod 400 includes the functions shown in blocks 402 and 404. A varietyof methods can be performed using one or more of the functions shown inthe method 400 and one or more other functions described herein.Reference numbers included within the description of FIG. 4 are providedas examples, rather than to limit the description to only the particularconfiguration(s) including the components associated with the referencenumbers.

The method 400 may be performed by a first computing system, such as thecomputing system 102. Block 402 includes receiving, from a secondcomputing system, a message identifying a symptom of a first vehicle.For example, the computing system 102 may receive, from the computingsystem 108, a message indicating that a first vehicle's check enginelight is on. The message may be received via the network 104. Othersymptoms are possible, such as the first vehicle's engine won't start,the first vehicle's brake lights are out, etc. The message may indicatea make, model, sub-model, trim package, and/or year of manufacture ofthe first vehicle. For example, the message may indicate that the firstvehicle is a 2002 Toyota Celica GT. The first vehicle may belong to acustomer of a repair shop to which the customer has brought the firstvehicle for repair. The computing system 108 may receive input enteredby a repair technician that is working on the first vehicle. Thereceived input may represent information about the first vehicle that isincluded in the message sent by the computing system 108 to thecomputing system 102.

Block 404 includes sending a repair tip to the second computing system.For example, the computing system 102 may send the repair tip 500 ofFIG. 5 in the form of data to the computing system 108 (i.e., acomputing system from which the computing system 102 received themessage that included information about the first vehicle and thesymptom of the first vehicle). The repair tip 500 may be sent via thenetwork 104. The computing system 108 may then display the repair tip asshown in FIG. 5 for viewing by a repair technician or another user.

The repair tip 500 may include a title phrase 502, a complaint phrase504, cause phrases 506, 508, 512, 514, and 516, and a correction phrase518. The phrases 502-518 may be selected or generated by the computingsystem 102 based on information included in the message received by thecomputing system 102 from the computing system 108.

The title phrase 502 may include a brief summary of one or morediagnostic or corrective procedures performed with regard to a componentof an additional vehicle. (In the context of describing the repair tip500 herein, the “additional vehicle” may, in some cases, be at least twoadditional vehicles. That is, the repair tip 500 may include informationrelated to multiple vehicles that are similar to the first vehicle andhave had similar diagnostic or corrective procedures performed on themwith similar results.) The title phrase 502 includes “P0335, ReplacedCrankshaft Position Sensor.”

The complaint phrase 504 may describe a symptom of the additionalvehicle that indicated a potential problem or malfunction related to thecomponent of the additional vehicle. The complaint phrase 504 includes“The customer states the check engine light is on.”

The cause phrases 506-516 may describe respective diagnostic proceduresthat were performed on the component of the additional vehicle. Therepair tip 500 will generally include at least one “non-condemning”cause phrase, that is, a phrase that describes a procedure performed onthe additional vehicle that yielded a result insufficient to determinethat the component of the additional vehicle associated with the symptomis defective. In some examples, performing the procedure suggested bythe non-condemning phrase may help the repair technician working on thefirst vehicle discover an “easy fix” for the symptom such asreconnecting a wire or cleaning a corroded contact etc. The repair tip500 will also generally include at least one “condemning” cause phrase,that is, a phrase that describes a procedure performed on the additionalvehicle that yielded a result sufficient to determine that a componentof the additional vehicle associated with the symptom is defective. Insome examples, the procedure suggested by the condemning phrase may bemore time-consuming, expensive, or burdensome than procedures suggestedby non-condemning phrases, but at times it may be necessary to performsuch procedures so that a component can be properly diagnosed ortroubleshooted. The phrases 506, 508, 512, and 514 are examples ofnon-condemning phrases, whereas the phrase 516 is an example of acondemning phrase.

The (non-condemning) phrase 506 includes “Connected a scan tool andfound P0335 Crankshaft Position Sensor ‘A’ Circuit.” The(non-condemning) phrase 508 includes “Using the scan tool, monitored theengine speed parameter and found the parameter intermittently droppedout.” The (non-condemning) phrase 512 includes “Performed a visualinspection of the crankshaft position sensor, found no faults.” The(non-condemning) phrase 514 includes “Using a lab scope, measured forpower and ground at the crankshaft position sensor, and discovered bothpower and ground were present.” The (condemning) phrase 516 includes“Using the lab scope, monitored the crankshaft position sensor signaland learned that the signal intermittently dropped out.”

In other examples, the repair tip 500 may include more or fewer phrases.The cause phrases 506-516 describe respective procedures performed onthe additional vehicle that exhibited the same symptom as the firstvehicle (e.g., the check engine light was on). The computing system 102may store data (e.g., in a repair order or a repair record) related tothe respective procedures that were performed. In one example, such datamay be sent to the computing system 102 from a third computing system110 (e.g., data submitted by a different repair technician). Herein, itshould be understood that any of the phrases 506-516 may, in someexamples, describe respective procedures performed on separate vehicles,or on the same vehicle.

The (non-condemning) phrase 506 describes a first procedure performed onthe additional vehicle. In this context, the first procedure performedon the additional vehicle yielded a result insufficient to determinethat a component of the additional vehicle associated with the symptomis defective. As shown by the phrase 506, the first procedure mayinclude connecting a scan tool to the crankshaft position sensor circuitand having the scan tool return a diagnostic trouble code P0335. Theadditional vehicle may be associated with the first vehicle in variousways as described below. Thus, the information regarding the additionalvehicle may be useful for repairing the first vehicle.

The (non-condemning) phrase 508 describes a second procedure performedon the additional vehicle. In this context, the second procedureperformed on the additional vehicle yielded a result insufficient todetermine that a component of the additional vehicle associated with thesymptom is defective. As shown by the phrase 508, the second proceduremay include using a scan tool to monitor an engine speed parameter ofthe additional vehicle and finding that the engine speed parameterintermittently dropped out. Using a scan tool to find that that theengine speed parameter intermittently dropped out may be insufficient todetermine that the crankshaft position sensor of the additional vehicleis defective.

The (non-condemning) phrase 512 describes a third procedure performed onthe additional vehicle. In this context, the third procedure performedon the additional vehicle yielded a result insufficient to determinethat a component of the additional vehicle associated with the symptomis defective. As shown by the phrase 512, the third procedure mayinclude performing a visual inspection of the crankshaft position sensorand finding no faults. Performing a visual inspection of the crankshaftposition sensor and finding no faults may be insufficient to determinewhether the crankshaft position sensor of the additional vehicle isdefective.

The (non-condemning) phrase 514 describes a fourth procedure performedon the additional vehicle. In this context, the fourth procedureperformed on the additional vehicle yielded a result insufficient todetermine that a component of the additional vehicle associated with thesymptom is defective. As shown by the phrase 514, the fourth proceduremay include using a lab scope to measure for power and ground at thecrankshaft position sensor, and discovering that both the power andground were present. Using a lab scope to measure for power and groundat the crankshaft position sensor and finding that both the power andground were present may be insufficient to determine that the crankshaftposition sensor of the additional vehicle is defective.

The (condemning) phrase 516 describes a fifth procedure performed on theadditional vehicle. In contrast to the first, second, third, and fourthprocedures described by the respective phrases 506, 508, 512, and 514,the fifth procedure performed on the additional vehicle yielded a resultsufficient to determine that a component of the additional vehicleassociated with the symptom is defective. As shown by the phrase 516,the fifth procedure may include using a lab scope to monitor thecrankshaft position sensor signal, and learning that the crankshaftposition sensor signal intermittently dropped out. Using a lab scope tomonitor the crankshaft position sensor signal and finding that thecrankshaft position sensor signal intermittently dropped out may besufficient to determine that the crankshaft position sensor of theadditional vehicle is defective.

The correction phrase 518 describes a corrective procedure that wasperformed with regard to the component of the additional vehicle. Forexample, the phrase 518 includes “Replaced the crankshaft positionsensor, cleared codes, and performed a road test of the vehicle. Thecustomer's concern did not return.”

The repair tip 500 is shown as including eight phrases, but in otherexamples, repair tips may include any number of phrases. Such repairtips will generally include at least one non-condemning phrase and atleast one condemning phrase.

The method 400 may further involve generating the repair tip 500 bygenerating one or more of the phrases 502-518. In this context, sendingthe repair tip to the second computing system may include sending thegenerated phrases 502-518 to the second computing system.

For example, the computing system 102 may use various data stored atdata storage device 210 and the contents of the message received fromthe computing system 108 to generate the repair tip 500. For instance,the message received by the computing system 102 from the computingsystem 108 may indicate that the first vehicle is a 2002 Toyota CelicaGT and that the first vehicle's check engine light is on. In response,the computing system 102 may search data storage device 210 for datacorresponding to other vehicles that are associated with the firstvehicle and that had exhibited a check engine light that was on. Forinstance, the computing system 102 may search for records correspondingto 2000-2005 models of either Toyota Celica GT or GTS trim packages thatexhibited check engine lights that were on. The computing system 102 maysearch for data that is related to the first vehicle in other ways aswell. For example, the computing system 102 may search for data relatedto vehicles that differ in make, model, and/or year, but are known toshare common components. The computing system 102 may use such data togenerate the repair tip, including the phrases 502-518, to be sent tothe computing system 108.

For example, the computing system 102 may identify data that is storedat data storage device 210. Based on the contents of the messagereceived by the computing system 102 from the computing system 108, thecomputing system 102 may identify at least repair record groups 608,612, 614, 616, and 620 of data table 600 of FIG. 6 as containingrelevant data. That is, repair record groups 608-620 may each correspondto a vehicle that was manufactured between 2000-2005, is either a ToyotaCelica GT or a Toyota Celica GTS, and exhibited a check engine lightthat was on.

By further example, the computing system 102 may store a plurality ofphrase templates 708, 712, 714, 716, 720, and 722 of FIG. 7 at datastorage device 210. The computing system 102 may (e.g., randomly) selectthe phrase template 708 for insertion of the data 609, 611, and 613. Thecomputing system 102 may (e.g., randomly) select the phrase template 712for insertion of the data 615, 617, and 619. The computing system 102may (e.g., randomly) select the phrase template 714 for insertion of thedata 621, 623, and 625. The computing system 102 may (e.g., randomly)select the phrase template 716 for insertion of the data 627, 629, and631. In other examples, any of the phrase templates 708-722 could beassigned to different identified data, or phrase templates not shown inFIG. 7 may be assigned to various other data.

The phrase templates 708-722 may be cause phrase templates. Cause phrasetemplates may be used to generate cause phrases, that is, phrases thatdescribe diagnostic procedures performed on a component of a vehicle.Data from the fields “Associated Component,” “Tool or Technique Used,”“Diagnostic Action Performed,” and/or “Result of Diagnostic Action” ofdata table 600 may be inserted into cause phrase templates to generateeither a condemning or non-condemning cause phrase.

The computing system 102 may generate the phrase 508 by inserting thedata 609, 611, and 613 into the phrase template 708 respectively at datafields 709, 711, and 713. The computing system 102 may generate thephrase 512 by inserting the data 615, 617, and 619 into the phrasetemplate 712 respectively at data fields 715, 717, and 719. As thecomputing system 102 is generating the phrase 512, the computing system102 may determine that data 615 and 617 have redundant data “visualinspection.” Accordingly, the computing system 102 may remove theredundant recitation of “visual inspection” from the phrase 512. Thecomputing system 102 may generate the phrase 514 by inserting the data621, 623, and 625 into the phrase template 714 respectively at 721, 723,and 725. The computing system 102 may generate the phrase 516 byinserting the data 627, 629, and 631 into the phrase template 716respectively at 727, 729, and 731.

In some instances, the computing system 102 may non-randomly select aphrase template for inclusion within the repair tip 500. For example,the computing system 102 may determine that the phrase template 708 wasthe least recently selected phrase template of any of the phrasetemplates 708-722 stored by the computing system 102. In response, thecomputing system 102 may select the phrase template 708 based on thatdetermination. Any of the phrase templates 712-722 selected for use inthe repair tip 500 may be selected in any of the ways described herein.

In some examples, identifying data for inclusion in a phrase templatemay include determining that such data corresponds to a data field ofthe phrase template. Accordingly, inserting such data into the phrasetemplate may include inserting the data into the corresponding datafields of the phrase template.

For instance, the computing system 102 may store data indicating thatthe data fields 709, 711, and 713 correspond respectively to data fields“Tool or Technique Used,” “Diagnostic Action Performed,” and “Result ofDiagnostic Action” of data table 600. Accordingly, the computing system102 may determine that the data 609, 611, and 613 correspondrespectfully to the data fields 709, 711, and 713 of the phrase template708. After determining that the data 609, 611, and 613 correspondrespectfully to the data fields 709, 711, and 713, the computing system102 may insert the data 609, 611, and 613 into the data fields 709, 711,and 713, respectfully, thereby generating the phrase 708.

The computing system 102 may also store data indicating that the datafields 715, 721, and 727 correspond to the “Tool or Technique Used” datafield of data table 600, the data fields 717, 723, and 729 correspond tothe “Diagnostic Action Performed” data field of data table 600, and thedata fields 719, 725, and 731 correspond to the “Result of DiagnosticAction” data field of data table 600. Accordingly, the computing system102 may determine that the data 615, 617, and 619 correspondrespectively to the data fields 715, 717, and 719 of the phrase template712. The computing system 102 may also determine that the data 621, 623,and 625 correspond respectively to the data fields 721, 723, and 725 ofthe phrase template 714. The computing system 102 may also determinethat the data 627, 629, and 631 correspond respectively to the datafields 727, 729, and 731 of the phrase template 716.

As such, the computing system 102 may enter the data 609, 611, and 613into the data fields 709, 711, and 713, respectively, thereby generatingthe phase 508. The computing system 102 may also enter the data 615,617, and 619 into the data fields 715, 717, and 719, respectively,thereby generating the phrase 512. The computing system 102 may alsoenter the data 621, 623, and 625 into the data fields 721, 723, and 725,respectively, thereby generating the phrase 514. The computing system102 may also enter the data 627, 629, and 631 into the data fields 727,729, and 731, respectively, thereby generating the phrase 516.

The title phrase 502 may similarly be generated by selecting a titlephrase template from a group of title phrase templates stored by datastorage device 210. An example title phrase template may be “______,Replaced ______.” Data from data fields “Diagnostic Trouble Code (DTC)”(not shown) and “Associated Component” of the data table 600 may beinserted into the title phrase template to generate the title phrase502. The title phrase template used to generate title phrase 502 may beselected randomly from the group of title phrase templates, or the titlephrase template might be selected based on determining that the titlephrase template is the least recently selected title phrase template ofthe group. Other examples are possible.

The complaint phrase 504 may similarly be generated by selecting acomplaint phrase template from a group of complaint phrase templatesstored by data storage device 210. An example title phrase template maybe “The customer states that the ______.” Data from the data field“Symptom” of data table 600 may be inserted into the complaint phrasetemplate to generate the complaint phrase 504. The template used togenerate complaint phrase 504 may be selected randomly from the group ofcomplaint phrase templates, or the complaint phrase template might beselected based on determining that the complaint phrase template is theleast recently selected complaint phrase template of the group. Otherexamples are possible.

The non-condemning cause phrase 506 may be generated similarly to any ofthe cause phrases 508-516 discussed herein.

The correction phrase 518 may similarly be generated by selecting acorrection phrase template from a group of correction phrase templatesstored by data storage device 210. An example correction phrase templatemay be “Replaced the , cleared codes, and performed a road test of thevehicle. The customer's concern did not return.” Data from the datafield “Associated Component” of the data table 600 may be inserted intothe correction phrase template to generate the correction phrase 518.The correction phrase template may be selected randomly from the groupof correction phrase templates, or the correction phrase template mightbe selected based on determining that the correction phrase template isthe least recently selected correction phrase template of the group.Other examples are possible.

The method 400 may further involve determining that neither a firstprocedure nor a second procedure is a visual inspection procedure. Forexample, the computing system 102 may determine that the proceduredescribed by the phrase 508 is not a visual inspection procedure byexamining data 609, 611, or 613 and determining that the proceduredescribed by the phrase 508 is instead a procedure that involves a scantool. Likewise, the computing system 102 may determine that theprocedures described respectively by the phrase 514 and the phrase 516are not visual inspection procedures by examining data 621, 623, 625,627, 629, and/or 631 and determining that the procedures describedrespectively by the phrase 514 and the phrase 516 are procedures thatinvolve a lab scope.

The method 400 may further involve, based on determining that neither afirst procedure nor a second procedure is a visual inspection procedure,identifying additional data that (i) is stored by the first computingsystem, (ii) is associated with the symptom and the component of thefirst vehicle, and (iii) is associated with a visual inspectionprocedure.

For example, the computing system 102 may identify data 615, 617, and/or619 of repair record group 612 that corresponds to a visual inspectionprocedure. As shown, the data 615, 617, and 619 are associated with the“check engine light” symptom. For example, the phrase 512 may begenerated by inserting the data 615, 617, and 619 into the phrasetemplate 712 as described above. In this way, the computing device 102may ensure, in some examples, that the repair tip 500 includes at leastone phrase describing a visual inspection procedure. In such an example,the repair tip might include the phrases 512 and 516, but no other causephrases. In this case, the computing system 102 may be configured togenerate or select repair tips that include both (i) a condemning phraseand (ii) a non-condemning phrase that describes a visual inspectionprocedure.

The method 400 may further involve identifying data stored by thecomputing system 102 that is associated with (i) the make, the model, orthe year of manufacture of the additional vehicle, (ii) the symptom ofthe additional vehicle, and (iii) a first procedure performed on theadditional vehicle, and determining that the identified data correspondsto at least a predetermined amount (e.g., a threshold amount) of repairrecords stored by the computing system 102.

In one example, the predetermined amount of repair records may be 1200.Referring to FIG. 6, the computing system 102 may determine that therepair record group 608 includes 1000 repair records, the repair recordgroup 612 includes 1500 repair records, the repair record group 614includes 1250 repair records, and the repair record group 616 includes1500 repair records. Accordingly, in some examples, the computing system102 may include phrases 512, 514, and 516 in the repair tip 500 butmight exclude the phrase 508 from the repair tip 500. In some instances,a threshold comparison may occur before generation of the phrases suchthat the phrase 508 is not generated because the repair record group 608has less than the threshold number of repair orders.

In examples depicted in FIGS. 8 and 9, the computing system 102 maystore phrases 508 and 528 that make up a first plurality of phrases,phrases 512 and 532 that make up a second plurality of phrases, phrases514 and 534 that make up a third plurality of phrases, and phrases 516and 536 that make up a fourth plurality of phrases. The phrases 508-516and 528-536 may all be associated with the symptom (e.g., check enginelight is on) of the first vehicle. The computing system 102 may storeother phrases (not shown) that are not associated with the symptom ofthe first vehicle and/or are associated with other symptoms.

As shown, the phrase 508 may convey information equivalent toinformation conveyed by the phrase 528, yet the phrase 508 may includesyntax and/or word choice that differs from the phrase 528. The phrase512 may convey information equivalent to information conveyed by thephrase 532, yet the phrase 512 may include syntax and/or word choicethat differs from the phrase 532. The phrase 514 may convey informationequivalent to information conveyed by the phrase 534, yet the phrase 514may include syntax and/or word choice that differs from the phrase 534.The phrase 516 may convey information equivalent to information conveyedby the phrase 536, yet the phrase 516 may include syntax and/or wordchoice that differs from the phrase 536.

Based on data table 600, the computing system 102 may associate data609, 611, and 613 of phrases 508 and 528 with repair record group 608.Therefore, the computing system 102 may identify the phrases 508 and 528as being associated with the first vehicle and the symptom of the firstvehicle based on the content of the data fields “Make,” “Model,” “Year,”and “Symptom,” of repair record group 608. The computing system 102 mayassociate data 615, 617, and 619 of phrases 512 and 532 with repairrecord group 612. Therefore, the computing system 102 may identify thephrases 512 and 532 as being associated with the first vehicle and thesymptom of the first vehicle based on the content of the data fields“Make,” “Model,” “Year,” and “Symptom,” of repair record group 612. Thecomputing system 102 may associate data 621, 623, and 625 of phrases 514and 534 with repair record group 614. Therefore, the computing system102 may identify the phrases 514 and 534 as being associated with thefirst vehicle and the symptom of the first vehicle based on the contentof the data fields “Make,” “Model,” “Year,” and “Symptom,” of repairrecord group 614. The computing system 102 may associate data 627, 629,and 631 of phrases 516 and 536 with repair record group 616. Therefore,the computing system 102 may identify the phrases 516 and 536 as beingassociated with the first vehicle and the symptom of the first vehiclebased on the content of the data fields “Make,” “Model,” “Year,” and“Symptom,” of repair record group 616.

By further example, the computing system 102 may randomly ornon-randomly select the phrase 508 for use in the repair tip 500 insteadof the phrase 528. In other examples, the computing system 102 mayselect the phrase 528 instead of the phrase 508. Similarly, thecomputing system 102 may randomly or non-randomly select the phrase 512for use in the repair tip 500 instead of the phrase 532. In otherexamples, the computing system 102 may select the phrase 532 instead ofthe phrase 512. Also, the computing system 102 may randomly ornon-randomly select the phrase 514 for use in the repair tip 500 insteadof the phrase 534. In other examples, the computing system 102 mayselect the phrase 534 instead of the phrase 514. Additionally, thecomputing system 102 may randomly or non-randomly select the phrase 516for use in the repair tip 500 instead of the phrase 536. In otherexamples, the computing system 102 may select the phrase 536 instead ofthe phrase 516. In this context, sending the repair tip 500 to thesecond computing system 108 may include sending the selected phrase 508,the selected phrase 512, the selected phrase 514, and the selectedphrase 516 as part of the repair tip 500.

The method 400 may further involve determining that a second procedureis not a visual inspection procedure and selecting the first phrasebased on determining that the second procedure is not a visualinspection procedure. In this context, the first procedure described bythe first phrase may be a procedure that includes visual inspection ofthe component of the second vehicle.

For example, the computing system 102 may determine that the procedure“monitored the crankshaft position sensor signal” as described by thephrase 516 is not a visual inspection procedure. In response, thecomputing system 102 may select the phrase 512 for inclusion in therepair tip 500 because the procedure “visual inspection” described bythe phrase 512 is a visual inspection procedure.

The method 400 may further involve determining that neither a firstprocedure nor a second procedure is a visual inspection procedure, andbased on determining that neither the first procedure nor the secondprocedure is a visual inspection procedure, selecting a phrase stored bythe first computing system that is (i) associated with the symptom andthe component of the first vehicle and (ii) describes a visualinspection procedure. In this context, sending the repair tip mayinclude sending the phrase describing a visual inspection procedure tothe second computing system.

For example, the computing system 102 may determine that neither theprocedure “monitored the crankshaft position sensor signal” of phrase516 nor the procedure “monitored the engine speed parameter” of phrase508 is a visual inspection procedure. As a result, the computing system102 may select the phrase 512 for inclusion in the repair tip 500because the procedure “visual inspection” described by the phrase 512 isa visual inspection procedure. At times, describing a visual inspectionprocedure in the repair tip 500 may allow a repair technician to easilyrepair the first vehicle by performing a visual inspection.

In some examples, the computing system 102 may determine that the phrase508 was the least recently selected phrase of the phrases 508 and 528.Similarly, the computing system 102 may determine that the phrase 512was the least recently selected phrase of the phrases 512 and 532. Also,the computing system 102 may determine that the phrase 514 was the leastrecently selected phrase of the phrases 514 and 534. Additionally, thecomputing system 102 may determine that the phrase 516 was the leastrecently selected phrase of the phrases 516 and 536. Based on thesedeterminations, the computing system 102 may include phrases 508, 512,514, and 516 as part of the repair tip 500 that is sent to the computingsystem 108.

By further example, the phrases 508, 512, and/or 514 may be listedbefore the phrase 516 within the repair tip 500. Since the phrases 508,512, and 514 are non-condemning phrases and the phrase 516 is acondemning phrase, a repair technician operating the computing system108 may view the phrases 508, 512, and 514 before the phrase 516, anddecide to perform the procedures described respectively by the phrases508, 512, and 514 before performing the procedure described by thephrase 516. This may allow the repair technician to discover an “easyfix” for the symptom of the first vehicle (if possible) beforeperforming a more complicated or burdensome procedure.

In this way, any non-condemning phrase (e.g., phrases 508, 512, and 514)selected to be included in the repair tip 500 will generally appearwithin the repair tip 500 before any condemning phrase selected to beincluded in the repair tip 500 (e.g., phrase 516). Multiple phrasesselected for inclusion in the repair tip 500 may be sequenced based onone or more of (i) monetary cost of performing the respectiveprocedures, (ii) an estimated time required to perform the respectiveprocedures, and (iii) complexity of the respective procedures.

For example, after selecting the phrases 508, 512, and 514 for inclusionin the repair tip 500, the computing system 102 may determine a sequenceof the phrases 508, 512, and 514 based one or more of the respective (i)monetary costs of performing the respective procedures described by thephrases 508, 512, and 514, (ii) the estimated respective times requiredto perform the respective procedures described by the phrases 508, 512,and 514, and (iii) the complexity of the respective procedures describedby the phrases 508, 512, and 514. In the example depicted in FIG. 5, thephrase 508 is listed first, the phrase 512 is listed second, and thephrase 514 is listed third. This sequence may reflect the overall cost,time, and complexity of performing the respective procedures of thephrases 508, 512, and 514.

In some examples, the computing system 102 may identify the phrases 512and 532 as being associated with the make, the model, or the year ofmanufacture of the first vehicle and the symptom of the first vehiclebased on examining the data fields “Make,” “Model,” “Year,” and“Symptom” of the repair record group 612. In some examples, thethreshold amount of repair records may be 1200 (but other examples arepossible). By examining the data table 600, the computing system 102 maydetermine that the phrases 512 and 532 correspond to 1500 repairrecords, and based on that determination the computing system 102 mayinclude either the phrase 512 or 532 within the repair tip 500. In someexamples, the phrase 508 or the phrase 528 might not be included withinthe repair tip 500 because the repair record group 608 corresponds toonly 1000 repair records (less than 1200).

By further example, the computing system 102 may identify the phrases516, 536, 520, and 540 as being associated with the make, the model, orthe year of manufacture of the first vehicle and the symptom of thefirst vehicle based on examining the data fields “Make,” “Model,”“Year,” and “Symptom” of the repair record groups 616 and 620. Thecomputing system 102 may determine that the phrases 516 and 536correspond to 1500 repair records, whereas the phrases 520 and 540correspond to only 1300 repair records. Based on that determination, thecomputing system 102 may include either the phrase 516 or 536 within therepair tip 500 instead of the phrases 520 or 540, because 1500 isgreater than 1300.

IV. Conclusion

Example embodiments have been described above. Those skilled in the artwill understand that changes and modifications can be made to thedescribed embodiments without departing from the true scope of thepresent invention, which is defined by the claims.

Additional embodiments, based on the features or functions describedherein, can be embodied as a non-transitory computer-readable mediumstoring program instructions, that when executed by a processor of amachine, cause the machine to perform a set of functions, the set offunctions comprising the features or functions of the aspects andembodiments described herein.

We claim:
 1. A method performed by a computing system including: one ormore processors and a network interface, wherein the network interfaceis connected to the one or more processors and is operativelyconnectable to a vehicle communication link on-board a particularvehicle, the method comprising: receiving, by the one or moreprocessors, a set of search terms, wherein the set of search termsincludes a first term indicative of at least a portion of a vehicle typeidentifier associated with the particular vehicle and a second termindicative of a symptom exhibited by the particular vehicle;transmitting wirelessly, by the network interface to a communicationnetwork including a computing system off-board the particular vehicle, arequest for a repair tip, wherein the request includes the set of searchterms; receiving wirelessly, by the network interface, from thecomputing system off-board the particular vehicle via the communicationnetwork, the repair tip in response to the request, wherein the repairtip includes: a complaint phrase specifying a symptom of a vehiclemalfunction, a cause phrase specifying a procedure to diagnose thevehicle malfunction, wherein the procedure to diagnose the vehiclemalfunction refers to a second tool, a correction phrase specifying aprocedure to remedy the vehicle malfunction; displaying, by a displayconnected to the one or more processors, the repair tip, whereindisplaying the repair tip includes displaying the complaint phrase, thecause phrase, and the correction phrase; and performing the procedure todiagnose a component on the particular vehicle, wherein performing theprocedure includes using the second tool to monitor a parameter or tomeasure a signal.
 2. The method of claim 1, wherein the second tool tomonitor the parameter includes a scan tool.
 3. The method of claim 2,further comprising: reading a diagnostic trouble code set in theparticular vehicle using the scan tool.
 4. The method of claim 2,wherein the second tool to measure the signal includes a scope or ameter.
 5. The method of claim 1, wherein performing the procedure todiagnose the component on the particular vehicle further includesperforming a visual inspection of a component.
 6. The method of claim 1,further comprising: displaying, by the display, the second termindicative of the symptom exhibited by the particular vehicle, whereinreceiving the set of search terms includes receiving a selection of thesecond term displayed by the display.
 7. The method of claim 1, whereinthe first term indicates at least one of: a year of the particularvehicle, a make of the particular vehicle, a model of the particularvehicle, a sub-model of the particular vehicle, an engine of theparticular vehicle, a system of the particular vehicle, or a trimpackage of the particular vehicle.
 8. The method of claim 1, furthercomprising: displaying, by the display, the first term indicative of atleast the portion of the vehicle type identifier associated with theparticular vehicle, wherein receiving the set of search terms includesreceiving a selection of the first term displayed by the display.
 9. Themethod of claim 1, wherein the symptom is indicative of at least one: acheck engine light being on in the particular vehicle or a diagnostictrouble code.
 10. The method of claim 1, wherein the set of search termsincludes a third term indicative of a vehicle mileage or hours of engineuse.
 11. A computing system comprising: one or more processors, whereinthe one or more processors are configured to receive a set of searchterms, wherein the set of search terms includes a first term indicativeof at least a portion of a vehicle type identifier associated with aparticular vehicle and a second term indicative of a symptom exhibitedby the particular vehicle; a network interface connected to the one ormore processors and operatively connectable to a vehicle communicationlink on-board a particular vehicle, wherein the network interface isconfigured to wirelessly transmit a request for a repair tip to acommunication network including a computing system off-board theparticular vehicle, wherein the request includes the set of searchterms, wherein the network interface is configured to wirelesslyreceive, from the computing system off-board the particular vehicle viathe communication network, the repair tip in response to the request,wherein the repair tip includes: a complaint phrase specifying a symptomof a vehicle malfunction, a cause phrase specifying a procedure todiagnose the vehicle malfunction, wherein the procedure to diagnose thevehicle malfunction refers to a second tool, a correction phrasespecifying a procedure to remedy the vehicle malfunction; a displayconnected to the one or more processors, wherein the display isconfigured to display the repair tip, wherein displaying the repair tipincludes displaying the complaint phrase, the cause phrase, and thecorrection phrase; and a second tool configured to perform the procedureto diagnose a component on the particular vehicle, wherein performingthe procedure includes using the second tool to monitor a parameter orto measure a signal.
 12. The computing system of claim 11, wherein thesecond tool to monitor the parameter includes a scan tool.
 13. Thecomputing system of claim 12, further comprising: reading a diagnostictrouble code set in the particular vehicle using the scan tool.
 14. Thecomputing system of claim 12, wherein the second tool to measure thesignal includes a scope or a meter.
 15. The computing system of claim11, further comprising: displaying, by the display, the second termindicative of the symptom exhibited by the particular vehicle, whereinreceiving the set of search terms includes receiving a selection of thesecond term displayed by the display.
 16. The computing system of claim11, wherein the first term indicates at least one of: a year of theparticular vehicle, a make of the particular vehicle, a model of theparticular vehicle, a sub-model of the particular vehicle, an engine ofthe particular vehicle, a system of the particular vehicle, or a trimpackage of the particular vehicle.
 17. The computing system of claim 11,further comprising: displaying, by the display, the first termindicative of at least the portion of the vehicle type identifierassociated with the particular vehicle, wherein receiving the set ofsearch terms includes receiving a selection of the first term displayedby the display.
 18. The computing system of claim 11, wherein thesymptom is indicative of at least one: a check engine light being on inthe particular vehicle or a diagnostic trouble code.
 19. The computingsystem of claim 11, wherein the set of search terms includes a thirdterm indicative of a vehicle mileage or hours of engine use.